\section{Requirements Capture}


\section{Game Requirements Specification}

\subsection{Risk Factors}\label{subsect_riskfactors}
The most important risks within the Requirements Capture process relate to the level of participation of the potential user base.  If  there is limited interest in the game then the game then, this will have.  Lack of understanding of what my target users consider fun.  Inability to incorporate fun into the game.  
External factors include the limited amount of time the target audience  will have to play the game,  the prizes offered will not appeal to the user and will not encourage the potential user group to participate in the game.



\subsection{Non-Functional Requirements}\label{subsubsect_nonfunct_requirements}
\begin{itemize}
\item The game be secure so that a malicious user can not either increase their rankings or sabotage the game by manipulating their scores.
\item The game should encourage the user to provide a wide as possible range of labels as possible.
\item Should encourage the user to provide terms which are highly representative of the image.
\item The game should encourage the user to play the game multiple times, thus increasing the number of labeled images.
\end{itemize}


\subsubsection{Use Cases} - see appendicies. 

% This is the beginning of the CAPTCHA requirements
\section{CAPTCHA Requirements Specification}
These are the requirements which the 

\subsection{Risk Factors}

These include, but are not limited to,  insufficient understanding of how provide accessible web pages for a blind person.  This could occur in two ways:  
lack of understanding of the tools used to provide blind people with access to computers, or the inability to fully understand how a blind person perceives the information.  The client not fully specifying what is needed, implying use cases that are not necessary and the misunderstanding of information conveyed.

%It is also possible that Not fully documenting meeting minutes, interview with the client and group discussions could result in the exclusion of necessary requirements to the system as the project develops.


\subsection{Non-Functional Requirements}\label{subsubsect_nonfunct_requirements}

\begin{itemize}
\item The system should not require excessive resources which would limit its uptake to organisations with vast resources in time and computational power.
\item The CAPTCHA must not require the use of web technology which does not operate with screen reader tools.
\item The CAPTCHA must be designed to meet the levels of usability required by blind people.
\end{itemize}

\subsubsection{Use Cases} - see appendicies.
